Monitoring users of a computer network

ABSTRACT

Communicating with and/or monitoring of a targeted used in computer-network environment (e.g., an instant messaging system) involves detecting that the targeted user has signed on to the network, and upon detecting the signon, automatically communicating with the targeted user, for example, by sending an instant message previously specified by a targeting user. Alternatively, or in addition, the targeting user can receive notification that the targeted user has signed on and/or that the instant message has been sent. Instead of, or in addition to, automatically sending an instant message and/or notifying the targeting user, a predefined operation specified by the targeting user (e.g., operating system command, script or executable file) can be performed. These various operations can be performed on one or more client systems, on one or more server systems, or any combination thereof.

TECHNICAL FIELD

This application relates to monitoring users of a computer network, forexample, to facilitate messaging between users in an online computerservices environment.

BACKGROUND

The computer system 100 illustrated in FIG. 1 represents a typicalhardware setup for executing software that allows a user to performtasks such as communicating with other computer users, accessing variouscomputer resources, and viewing, creating, or otherwise manipulatingelectronic content—that is, any combination of text, images, movies,music or other sounds, animations, 3D virtual worlds, and links to otherobjects. The system includes various input/output (I/O) devices (mouse103, keyboard 105, display 107) and a general purpose computer 100having a central processor unit (CPU) 121, an I/O unit 117 and a memory109 that stores data and various programs such as an operating system111, and one or more application programs 113. The computer system 100also typically includes some sort of communications card or device 123(e.g., a modem or network adapter) for exchanging data with a network127 via a communications link 125 (e.g., a telephone line).

As shown in FIG. 2, a user of a computer system can access electroniccontent or other resources either stored locally at the user's ownclient system 202, 202 a, or 202 b (for example, a personal or laptopcomputer) or remotely at one or more server systems 200. An example of aserver system is a host computer that provides subscribers with onlinecomputer services such as e-mail, e-commerce, chat rooms, Internetaccess, electronic newspapers and magazines, etc.

Users of a host computer's online services typically communicate withone or more central server systems 200 through client software executingon their respective client systems 202, 202 a, or 202 b. In practice, aserver system 200 typically will not be a monolithic entity but ratherwill be a network of interconnected server computers, possiblyphysically dispersed from each other, each dedicated to its own set ofduties and/or to a particular geographical region. In such a case, theindividual servers are interconnected by a network of communicationlinks, in know on fashions. One such server system is “America Online4.0” from America Online, incorporated of Virginia (also known as“AOL”).

One increasingly popular computer network-based activity is referred toas “instant messaging.” An instant message is a form of electroniccommunication between users of a computer network in which a windowpops-up on the recipient's computer screen “instantly” and without therecipient's having to access an e-mail program or otherwise check formessages. An instant message appears essentially as soon as the messagesender clicks the send button subject to any time or propagation delaysthe message may have encountered on the network. In comparison to moste-mail applications, instant messaging enables users to communicate witheach other in a more dynamic, urgent and interactive manner.

FIG. 3 is a screen shot of an Instant Message (IM) window 30 as used inAOL's Instant Messenger (“AIM”) system. As shown therein, the window 30includes a text display area 31 and text entry area 32. Both usersinvolved in the IM under consideration (i.e., sender and recipient)would have a similar window displayed on his or her computer monitor.When one user (PhillipsJC) types a comment 34 in text entry area 32 andclicks the Send button 33 (or, depending on the configuration, pressesthe “ENTER” key on the keyboard), the entered text (e.g., “Hey, did yousee the game last night?”) is displayed in the text display area 31 ofthe window 30 such that it is visible to both users. After FRsnafuenters a comment 35 in response and clicks the Send button 33, thatcomment 35 appears in the text display area 31 underneath the previouscomment 34. This exchange of comments continues indefinitely until theusers decide to terminate the exchange.

Typically, instant messages can be sent to another user only when thatuser is presently signed on to the computer service. Users who aresigned off are unavailable to receive instant messages. Accordingly,another popular innovation introduced by America Online is the “BuddyList,” which allows users to monitor when other specified users(“buddies”) are signed onto and/or off of the computer service underconsideration (e.g., AOL Instant Messenger).

As shown in FIG. 4, the Buddy List is implemented as a window 40 thatlists specified users, or buddies, who are signed on to the AIM system.In the example shown, the Buddy List for user “PhillipsJC” indicatesthat four of PhillipsJC's buddies 41-44 currently are signed on to thesystem and thus available to receive instant messages. The Buddy List isupdated based on information received from a server to add or deletenames of buddies as they sign on and off, respectively. Such Buddy Listupdates can be accompanied by various audible and visual indications tohelp notify the user that a buddy has signed on or off.

Despite the various notification mechanisms, a user nevertheless mayfail to notice that a buddy with whom IM communication is desired hassigned on to the system. For example, if the user is on the telephone oraway from his or her office, one of that user's buddies may sign on andthen off again unnoticed by the user. Alternatively, or in addition,even when a user notices that a buddy has signed on to the system, theuser nevertheless may be unable to send the buddy an IM because the usermay be otherwise engaged (e.g., in a meeting).

Other reasons exist why a user might not notice that a buddy has signedon and/or miss an opportunity to send an IM to the buddy. For example,the user might have so many buddies on his buddy list that they cannotall fit on the display screen, or in a display window, at the same time.Moreover, the buddy list window might be obscured by other windows orobjects and thus the user might not be able to notice when the buddy hassigned on. In any of these and possibly other situations, the buddy maysign off of the system before the user is able to send an IM, thusmissing the window of opportunity.

Accordingly, the present inventor recognized that it would be desirableto provide users with mechanisms for monitoring signons by buddiesand/or communicating with the buddies immediately and automatically upontheir signing on to the system.

SUMMARY

Implementations may include various combinations of the followingfeatures.

In one aspect, a computer-implemented method of communicating with auser includes detecting that a previously unavailable user is availableto receive messages, and automatically sending a predetermined message(e.g., an instant message) to the user upon detecting that the user hasbecome available. Alternatively, or in addition, notification may beprovided to a monitoring user that the previously unavailable user hasbecome available and/or that the predetermined message was sent. Themethod may further include instantiating an instant messaging window ona computer screen of the monitoring user upon detecting that thepreviously unavailable user has become available. Optionally, thenotified monitoring user may have previously specified the predeterminedmessage. Moreover, a command specified by the monitoring user (e.g., anoperating system command, a script, or an executable file) may beexecuted upon detecting the user's availability.

Prior to the detection, a request may have been received from themonitoring user to monitor availability of the previously unavailableuser. The received request may be queued until the previouslyunavailable user becomes available. The automatic sending of thepredetermined message may include instantiating a window on the user'scomputer screen displaying the predetermined message. The operations ofdetecting and the automatic message sending may be repeated each timethe user newly becomes available. Moreover, the detecting and automaticmessage sending operations may be performed entirely on one or moreserver systems, entirely on one or more client systems, or in adistributed manner among one or more server systems and one or moreclient systems.

In another aspect, a computer-implemented instant messaging method mayinclude detecting that a targeted user has signed on to an instantmessaging service, and upon detecting the signon, automatically sendingto the targeted user an instant message previously specified by atargeting user. The targeting user can receive notification that thetargeted user has signed on to the instant messaging service and/or thatthe instant message was sent.

Automatically sending the instant message may include instantiating awindow on the targeted user's computer screen displaying the instantmessage and/or instantiating an instant messaging window on a computerscreen of the targeting user upon detecting that the targeted user hassigned on.

Prior to detection, a request may be received from the targeting user tomonitor a signon by the targeted user. The received request may bequeued until the targeted user signs on. The targeting user also mayprovide input specifying the instant message.

In another aspect, a computer-implemented method of monitoring users ofa computer network may include receiving from a monitoring user arequest to monitor availability of a monitored user, detecting that themonitored user is available (e.g., has signed on), and automaticallyperforming a predefined operation specified by the monitoring user(e.g., send an instant message, provide notification to the monitoringuser or another entity, or both, and/or execute an operating systemcommand, a script, or an executable file) upon detecting that themonitored user is available.

In another aspect, a computer-implemented method, performed at a server,of communicating with a user on a computer network including a pluralityof clients and at least one server, may include receiving a request todetect when a currently unavailable user becomes available to receivemessages, detecting that the user has become available, andautomatically sending a predetermined message to the user upon detectingthat the user has become available.

In another aspect, a computer-implemented method, performed at a client,of communicating with a user on a computer network including a pluralityof clients and at least one server, may include generating a request todetect when a currently unavailable user becomes available to receivemessages, receiving notice that the user has become available, andautomatically sending a predetermined message to the user.

In another aspect, an instant messaging system may include a serversystem and one or more client systems, each associated with acorresponding user, in communication with the server system. The serversystem may include software instructions for (i) monitoring a targeteduser's availability to receive instant messages, and (ii) sending anotification that a targeted user has become available to receiveinstant messages. Each of the one or more client systems may includesoftware instructions for (i) queuing a request to send an instantmessage to a currently unavailable targeted user, and (ii) sending theinstant message to the targeted user upon receiving notification fromthe server system that the targeted user has become available to receiveinstant messages.

One or more of the following advantages may be provided. The techniquesand methods described here enable users to more reliably and efficientlytrack the comings and goings of their buddies. As a result, thelikelihood of a user's being able to communicate (e.g., by instantmessage) with buddies, even those who sign on to the computer serviceinfrequently or sporadically, is enhanced dramatically.

In addition, communication between users is improved by providingmechanisms to automatically and instantly communicate with buddies upontheir signing on to the computer service. The sending user needs neitherto be aware of the buddy's signing on, nor be available to send an IM,for this automatic and instant communication to occur. Rather, thesending user needs only to set up the “pounce” and the buddy at whom thepounce is targeted can receive an IM automatically and without requiringthe sending user's further attention or authorization.

The details of one or more embodiments are set forth in the accompanyingdrawings and the description below. Other features, objects, andadvantages of the invention will be apparent from the description anddrawings, and from the claims.

DRAWING DESCRIPTIONS

FIG. 1 is a block diagram of a computer system.

FIG. 2 shows a typical network computing environment.

FIG. 3 is a screen shot of an “Instant Message” window.

FIG. 4 is a screen shot of a “Buddy List” window in AOL's InstantMessenger for Windows.

FIG. 5 is a flowchart of pouncing on a user.

FIG. 6 is a screen shot of a “Buddy List” window in AOL InstantMessenger for Unix.

FIG. 7 is a screen shot of a “Tools” pull-down menu in the Buddy Listwindow of FIG. 6.

FIG. 8 is a screen shot of a “Create New Pounce” window.

FIG. 9 is a screen shot of an instant message window corresponding tothe Create New Pounce window of FIG. 8.

FIG. 10 is screen shot of a “Conversation” window.

FIG. 11 is a screen shot of a “Send IM” window.

FIG. 12 is another screen shot of a “Tools” pull-down menu in the BuddyList window of FIG. 6.

FIG. 13 is a screen shot of an “Edit Pounce” window.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

FIG. 5 is a flowchart of a process that allows one user to “pounce” onanother user (e.g., a buddy) as soon as the buddy signs on to thecomputer service. “Pounce” refers to the ability to take one or morespecified actions (e.g., send a message, emit an audible or visualnotification, execute a command, etc.) automatically upon determiningthat a specified event has occurred, for example, detecting that a buddyhas signed on to the computer service.

As shown in FIG. 5, as an initial step in pouncing on another user (the“pouncee” or “targeted user”), a first user (the “pouncer” or “targetinguser”) sets up the parameters of the pounce (step 50). Although theseparameters can vary between implementations, typical parameters thatcould be specified by the pouncer include the identity of the pouncee(specified by, e.g., signon ID, name, e-mail address, etc.); the eventthat triggers the pounce (e.g., pouncee's signing on to system,pouncee's sending an IM to a specified party, detection of being addedto or deleted from the pouncee's buddy list, etc.); the action oractions that are to be taken (e.g., send an IM; send a chat invitation,audible or visual notification, execute a specified command, or anyother arbitrary action); and whether the pounce should occur only onceor upon each separate detection of the specified trigger event. Thepouncee designated in step 50 can, but need not necessarily, be on thepouncer's Buddy List.

After being set-up by the pouncer, the pounce is queued pendingoccurrence of the specified event (step 51). In effect, an indication isset at the server that the pouncer's client application is to benotified upon detection of the specified event. The queue can bemaintained either locally at the pouncer's client system or remotely ata server system. Either a single pounce or multiple pounces can be inthe queue concurrently. In addition, a pounce can be either asingle-shot (i.e., executed only once on the first occurrence of thespecified event) or persistent (i.e., executed with each occurrence ofthe specified event).

The next step is to wait for occurrence of the specified event (step52), for example, a detection that a specified user has signed on to thecomputer service. This detection can occur either at the client systemor in conjunction with a server on the network.

Next, upon occurrence of the specified event, the pounce is executed(step 53). Execution of the pounce can occur at the pouncer's clientsystem or at the pouncee's client system, or both, potentially inconjunction with one or more server systems. The particular actions thatcan be taken upon execution of the pounce can vary with differentimplementations, and/or based on user-specified preferences. Typicalactions may include one or more of the following: sounding an alarm(step 54); sending an IM (step 55), opening a conversation window on thepouncer's client system (step 56); or executing a user-specified command(step 57), for example, locally on the pouncer's client system. Asindicated by dotted lines, each of the actions indicated in steps 54-57is optional. Moreover, other actions beyond or in addition to thoseshown in steps 54-57 may be taken.

After the pounce has been executed, it is determined whether or not thepounce is persistent—that is, whether or not the pounce should beexecuted only once or each time upon detection of the specified event(step 58). If the pounce is persistent, it remains in the queue and theprocess returns to step 52 to wait for the next specified event. On theother hand, if the pounce is a single-shot, the pounce is removed fromthe queue (step 59) and the process returns to step 50 to allow thepouncer to set up another pounce, as desired.

A single user can have multiple pounces pending at the same time. Theprocess shown in FIG. 5 generally represents steps that are taken foreach individual pounce sequence.

FIGS. 6-13 are screen shots illustrating an implementation of the pounceconcept in a Unix-based version of the AIM application (referred to as“TiK”). FIG. 6 shows a TiK Buddy List window 60 for user “FRsnafu”displaying a list 61 of three of FRsnafu's buddies 62 currently signedon to the AIM system. The Buddy List window 60 also includes a menu bar67 listing three drop-down menus (File, Tools, Help), a text area 66 forentering text strings for web searches, an IM button 63 forinstantiating an IM window to send an IM to another user, an Info button64 for retrieving information about another user, and a Chat button 65for instantiating a Chat window to invite another user to participate ina chat session.

As noted above, the Buddy List window 60 in FIG. 6 indicates that threeof FRsnafu's buddies 62 currently are signed on to AIM. However, in thisexample, user FRsnafu desires to send an IM to another buddy,“PhillipsJC,” who is not currently signed on to the AIM system.Accordingly, FRsnafu, the pouncer in this example, decides to set up apounce to receive notification, and to send PhillipsJC an IM, as soon asPhillipsJC signs on to AIM.

FIG. 7 is a screen shot of the Tools drop-down menu 70, which thepouncer accesses to set up a pounce. As shown therein, the pouncerselects menu option “Buddy Pounce” 72, which in turn brings up asub-menu displaying a single option 73, “New Pounce,” that enables thepouncer to set up the desired pounce.

FIG. 8 shows a “Create New Pounce” window 80 which is displayed on thepouncer's screen in response to selection of the “New Pounce” option 73.As shown in FIG. 8, the Create New Pounce window 80 includes a namefield 81 into which the pouncer enters the name of the pouncee—i.e., thebuddy who is the subject of the pounce. The window 80 also includes fivecheck-boxes 82-86 that the pouncer can check or not to selectivelyactivate five corresponding features.

If the pouncer checks box 82, a blank IM window 110 (FIG. 11) will popup on the pouncer's screen when the pouncee signs on to the AIM system.Under this option, an IM is not sent automatically to the pouncee, butrather the IM interface window is merely instantiated to allow thepouncer to easily and quickly enter appropriate text and send an IM tothe pouncee.

In contrast, if the pouncer checks box 83 in window 80 (FIG. 8), an IMwill be sent to the pouncee automatically, and will pop up on thepouncee's screen, as soon as the pouncee signs on to AIM. This automaticsending of an IM is performed transparently as a consequence of the AIMsystem detecting the specified event (i.e., the pouncee's signing on)and without any input or response on the part of the pouncer beyondinitially setting up the pounce. The particular text to be included inthe IM sent to the pouncee—“Gotcha!”—is specified by the pouncer inmessage field 87.

FIG. 9 is a screen shot of the Instant Message window 90 that pops up onthe pouncee's window upon signing on to AIM. As shown, the window 90includes a text display area 93 showing the identity 91 of the IM sender(i.e., the pouncer) and the message 92 (“Gotcha!”) specified by thepouncer.

When the pouncer designates by checking box 83 (FIG. 8) that an IMshould sent to the pouncee automatically, the Tik application alsoautomatically instantiates a “Conversation” window 102 on the pouncer'sclient system, as shown in FIG. 10. Essentially, the Conversation window102 fulfills the same function as the Instant Message window 30 shown inFIG. 3. Specifically, the Conversation window 102 includes a textdisplay area 112, a text entry area 116, and buttons 118 to allow theuser to control various aspects of the IM presentation and exchange. Asshown in FIG. 10, the text display area 112 in window 102 includes asingle line of text corresponding to the IM automatically sent to thepouncee upon execution of the pounce. This single line includes a timefield 104 showing the time at which the IM was sent, a name field 106showing the IM sender's identity, and a message field 108 showing themessage.

Checking box 84 in window 80 (FIG. 8) causes a “Pounce Sound” (i.e., anaudible notification) to be played on the pouncer's client system uponexecution of the pounce. The Pounce Sound notifies the pouncer that thepouncee has signed on to the AIM system.

Box 85 in window 80 determines whether the pounce should be asingle-shot or persistent. In the example shown, box 85 is unchecked sothe pounce being set up in FIG. 8 will be persistent—that is, it willexecute with each detection of a signon by the pouncee. In contrast, ifbox 85 was checked, the pounce would execute only once upon nextdetecting a signon by the pouncee and then would be deleted from thepounce queue.

By checking box 86 in window 80 (FIG. 8), the pouncer can specify acommand (for example, a operating system command, a script, or anexecutable file) that is to be executed as part of the pounce execution.The particular command to be executed—in this example, an executablefile at the path “c:\notify.exe” —is specified by the pouncer in textentry area 88 and can be virtually any command that is executable by thepouncer's client system. For example, the notify.exe command could sendan IM to one or more third parties informing them that the pouncee hassigned on. Alternatively, or in addition, notify.exe could launchanother application (e.g., an online computer game to play with thepouncee) or initiate virtually any other arbitrarily-complex orarbitrarily-simple computer-controlled operation.

When the pouncer has set up the new pounce with the desired parameters,the pouncer clicks button 89 (FIG. 8) and the pounce is then saved inthe queue of currently pending pounces.

As noted above, a single user can have more than one pounce pending inthe queue at the same time. FIG. 12, for example, shows a Buddy Listsub-menu 120 for a pouncer who has three pounces 122, 124 and 126concurrently queued up and pending. Each of these pounces 122, 124, 126is individually configurable as described above with regard to FIG. 8.

Moreover, a queued pounce can be modified as desired by selecting itfrom the sub-menu 120, which in turn brings up an “Edit Pounce” window130 as shown in FIG. 13. The Edit Pounce window 130 essentially is thesame as the Create New Pounce window 80 shown in FIG. 8, except that theEdit Pounce window 130 is presented to the pouncer with the data fieldsand check boxes selectively filled in according to the pounce's currentparameter set. The pouncer can modify any of these parameters bychecking or unchecking boxes 132-136, and/or changing the text in fields137-139. Once the pounce's parameters have been modified as desired, thepouncer can save the modified pounce in the queue by clicking the OKbutton 141. Alternatively, the pouncer can delete the pounce from thequeue by clicking the Delete button 140.

The techniques, methods and systems described here may findapplicability in any computing or processing environment in whichmonitoring other users and/or communicating with them is desirable. Inparticular, the concept of pouncing on another user could be applied toother media such as internet TV, cellular telephones, pagers, two-wayradios, etc. For example, a cellular telephone service provider couldimplement a system in which a queued-up telephone call was completed assoon as the intended recipient turned on his or her cell phone.

Various implementations of the systems and techniques described here maybe realized in digital electronic circuitry, or in computer hardware,firmware, software, or in combinations thereof. A system or otherapparatus that uses one or more of the techniques and methods describedhere may be implemented as a computer-readable storage medium,configured with a computer program, where the storage medium soconfigured causes a computer system to operate on input and/or generateoutput in a specific and predefined manner. Such a computer system mayinclude one or more programmable processors that receive data andinstructions from, and transmit data and instructions to, a data storagesystem, and suitable input and output devices.

Each computer program may be implemented in a high-level procedural orobject-oriented programming language, or in assembly or machine languageif desired; and in any case, the language may be a compiled orinterpreted language. Suitable processors include, by way of example,both general and special purpose microprocessors.

Generally, a processor will receive instructions and data from aread-only memory and/or a random access memory. Storage devices suitablefor tangibly embodying computer program instructions and data includeall forms of non-volatile memory, including semiconductor memorydevices, such as EPROM, EEPROM, and flash memory devices; magnetic diskssuch as internal hard disks and removable disks; magneto-optical disks;and CD-ROM disks.

Any of the foregoing may be supplemented by, or implemented in,specially-designed ASICs (application-specific integrated circuits).

A number of embodiments have been described. Nevertheless, it will beunderstood that various modifications may be made without departing fromthe spirit and scope of the invention. Accordingly, other embodimentsare within the scope of the following claims.

What is claimed is:
 1. A computer implemented method of monitoring usersof a computer network, the method comprising: receiving from amonitoring user a request to monitor the availability of a monitoreduser to receive messages; detecting whether the monitored user isavailable; and executing a command based on whether the monitored useris available, the command being specified by the monitoring user andperforming a function other than alerting the monitoring user of theavailability of the monitored user, the command comprising an executablefile, a scrip, or an operating system command.
 2. The method of claim 1wherein receiving the request includes receiving a request to monitorthe availability of a previously unavailable user.
 3. The method ofclaim 2 wherein the command is executed upon detecting that thepreviously unavailable user has become available.
 4. The method of claim1 further comprising automatically sending a predetermined message tothe monitored user based on whether the monitored user is available. 5.The method of claim 4 further comprising repeating the detecting,executing, and automatic sending each time the monitored user newlybecomes available.
 6. The method of claim 1 wherein the detecting andexecuting are performed entirely on one or more server systems.
 7. Themethod of claim 1 wherein the detecting and executing are performedentirely on one or more client systems.
 8. The method of claim 1 whereinthe detecting and executing are distributed among one or more serversystems and one or more client systems.
 9. The method of claim 1 furthercomprising repeating the detecting and executing each time the monitoreduser newly becomes available.
 10. The method of claim 1 wherein themonitoring user is an operator of a computer who is interested inunderstanding the availability of the monitored user to receivemessages.
 11. The computer system of claim 1 wherein the monitoring useris an operator of a computer who is interested in understanding theavailability of the monitored user to receive messages.
 12. The methodof claim 1 wherein executing a command comprises executing a commandthat launches an online computer game to play with the monitored user.13. The method of claim 1 wherein executing a command comprisesexecuting a command not directed to monitoring online status.
 14. Themethod of claim 1 wherein executing a command comprises executing acommand that sends to the monitored user a message from the monitoringuser.
 15. The method of claim 1 wherein executing a command comprisesexecuting a command that displays to the monitored user a message fromthe monitoring user.
 16. The method of claim 15 wherein displaying amessage comprises visually displaying a message to the monitored user.17. The method of claim 15 wherein the message comprises an instantmessage sent by the monitoring user to the monitored user.
 18. Themethod of claim 17 wherein the instant message is sent to only themonitored user.
 19. A computer system including a computer program formonitoring users of a computer network, the computer program includingcode segments structured and arranged to: receive from a monitoring usera request to monitor the availability of a monitored user to receivemessages; detect whether the monitored user is available; and execute acommand based on whether the monitored user is available, the commandbeing specified by the monitoring user and performing a function otherthan alerting the monitoring user of the availability of the monitoreduser, and comprising an executable file, a script, or an operatingsystem command.
 20. The computer system of claim 19 wherein thereceiving code segment includes a code segment for receiving a requestto monitor the availability of a previously unavailable user. 21.Thecomputer system of claim 20 wherein the executing code segment includesa code segment for executing the command upon detecting that thepreviously unavailable user has become available.
 22. The computersystem of claim 19 further comprising a code segment for automaticallysending a predetermined message to the monitored user based on whetherthe monitored user is available.
 23. The computer system of claim 22further comprising a code segment for repeating the detecting,executing, and automatic sending each time the monitored user newlybecomes available.
 24. The computer system of claim 19 wherein the codesegments for detecting and executing are located entirely on one or moreserver systems.
 25. The computer system of claim 19 wherein the codesegments for detecting and executing are located entirely on one or moreclient systems.
 26. The computer system of claim 19 wherein the codesegments for detecting and executing are distributed among one or moreserver systems and one or more client systems.
 27. The computer systemof claim 19 further comprising a code segment for repeating thedetecting and executing each time the monitored user newly becomesavailable.
 28. The system of claim 19 wherein the execute a command codesegment comprises a code segment structured and arranged to launch anonline computer game to play with the monitored user.
 29. The system ofclaim 19 wherein the execute a command code segment comprises a codesegment structured and arranged to execute a command not directed tomonitoring online status.
 30. The system of claim 19 wherein the executea command code segment comprises a code segment structured and arrangedto send to the monitored user a message from the monitoring user. 31.The system of claim 19 wherein the execute a command code segmentcomprises a code segment structured and arranged to display to themonitored user a message from the monitoring user.
 32. The system ofclaim 31 wherein the execute a command code segment is structured andarranged to visually display a message to the monitored user.
 33. Thesystem of claim 31 wherein the message comprises an instant message sentby the monitoring user to the monitored user.
 34. The system of claim 33wherein the instant message is sent to only the monitored user.
 35. Anapparatus for monitoring users of a computer network, the apparatuscomprising: means for receiving from a monitoring user a request tomonitor the availability of a monitored user to receive messages; meansfor detecting whether the monitored user is available; and means forexecuting a command based on whether the monitored user is available,the command being specified by the monitoring user and performing afunction other than alerting the monitoring user of the availability ofthe monitored user, and comprising an executable file, a script, or anoperating system command.